-
Notifications
You must be signed in to change notification settings - Fork 586
#354 | track publishing failures #357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@slayful Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
|
@slayful Thank you for signing the Contributor License Agreement! |
acogoluegnes
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This also needs a test in MetricsCollectorTest (it's just a mock test).
|
|
||
| void basicPublish(Channel channel); | ||
|
|
||
| void basicPublishFailure(Channel channel); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd add the thrown exception as a second parameter. Our implementations wouldn't use it, but external ones could.
|
Thanks for this contribution @slayful! I reviewed the PR, it doesn't need much change. Note this is a breaking change as it adds a method to an existing interface (I changed the PR summary to reflect this). |
|
Hey, @acogoluegnes I've addressed the feedback, so if you could take a look that would be great. I can see that concourse-ci's not passing though I don't have access there. I'm currently running the tests on my localhost, and they're looking good so far. |
|
Ah, you already did, thank you! :) |
|
@slayful The Concourse failure was something else actually, but it's fixed now. Just waiting a bit more before merging, in case @michaelklishin comes up with something to change. |
|
I at first expected this to include what's apparently in #360. That's fine. Perhaps we should add some docs about what exactly counts as a failure at the moment, since unroutable messages and negative acks will be separate metrics. |
Proposed Changes
References #354, followed up with #360.
Types of Changes
Checklist
CONTRIBUTING.mddocument